Welcome Guest. Please Login or Register  


You are here: Index > AMPPS > General Support > Topic : upgrade to 2.3, all sited "database error"

1


Threaded Mode | Print  

 upgrade to 2.3, all sited "database error", after 2.3 u/g "Error establishing a database connection" everywhere (17 Replies, Read 20919 times)
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
Just upgraded to 2.3 and get only "Error establishing a database connection" message when trying to load any site (63) other than //localhost/ampps/

I can see and browse all of my databases, but not a page will load.

There is a triangular 'warning' icon <?> icon in myphpadmin I've not seen before. (attached)

Error logs show only errors from 2013:
Quote
[21-Oct-2013 23:28:40] FATAL : 1 Maximum execution time of 30 seconds exceeded C:\AMPPS\ampps\softaculous\enduser\softpanel.php 1577
[21-Oct-2013 23:28:40] FATAL : 1 Maximum execution time of 30 seconds exceeded C:\AMPPS\ampps\softaculous\enduser\softpanel.php 1577


I'm dead in the water.
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
restart, mysql error logs:

Code

2014-02-25 23:46:49 12772 [Warning] You need to use --log-bin to make --binlog-format work.
2014-02-25 23:46:49 12772 [Note] Plugin 'FEDERATED' is disabled.
2014-02-25 23:46:49 12772 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-02-25 23:46:49 12772 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-25 23:46:49 12772 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-25 23:46:49 12772 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-25 23:46:49 12772 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-25 23:46:49 12772 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-02-25 23:46:49 12772 [Note] InnoDB: Completed initialization of buffer pool
2014-02-25 23:46:49 12772 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-25 23:46:50 12772 [Note] InnoDB: 128 rollback segment(s) are active.
2014-02-25 23:46:50 12772 [Note] InnoDB: Waiting for purge to start
2014-02-25 23:46:50 12772 [Note] InnoDB: 5.6.16 started; log sequence number 380761775
2014-02-25 23:46:50 12772 [Note] Server hostname (bind-address): '*'; port: 3306
2014-02-25 23:46:50 12772 [Note] IPv6 is available.
2014-02-25 23:46:50 12772 [Note]  - '::' resolves to '::';
2014-02-25 23:46:50 12772 [Note] Server socket created on IP: '::'.
2014-02-25 23:46:50 12772 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists.
2014-02-25 23:46:50 12772 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-02-25 23:46:50 12772 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists.
2014-02-25 23:46:50 12772 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists.
2014-02-25 23:46:50 12772 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-02-25 23:46:50 12772 [Note] Event Scheduler: Loaded 0 events
2014-02-25 23:46:50 12772 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16'  socket: ''  port: 3306  MySQL Community Server (GPL)


<?>
IP: --   

upgrade to 2.3, all sited "database error"
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Check if the Database User exists.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
Quote From : tidus February 26, 2014, 8:29 pm

Check if the Database User exists.


Hey! Thanks for your reply.  I was able to make some progress by restoring everything from a backup.  But there are still some issues with the installation that will prevent me from upgrading to 2.3. Error logs are below;


Code

2014-02-26 22:48:32 10272 [Note] Plugin 'FEDERATED' is disabled.
2014-02-26 22:48:32 10272 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-26 22:48:32 10272 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-26 22:48:32 10272 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-26 22:48:32 10272 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-26 22:48:32 10272 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-02-26 22:48:32 10272 [Note] InnoDB: Completed initialization of buffer pool
2014-02-26 22:48:32 10272 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-26 22:48:32 10272 [Note] InnoDB: 128 rollback segment(s) are active.
2014-02-26 22:48:32 10272 [Note] InnoDB: Waiting for purge to start
2014-02-26 22:48:32 10272 [Note] InnoDB: 5.6.14 started; log sequence number 380674201
2014-02-26 22:48:32 10272 [Note] Server hostname (bind-address): '*'; port: 3306
2014-02-26 22:48:32 10272 [Note] IPv6 is available.
2014-02-26 22:48:32 10272 [Note]  - '::' resolves to '::';
2014-02-26 22:48:32 10272 [Note] Server socket created on IP: '::'.
2014-02-26 22:48:32 10272 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-02-26 22:48:32 10272 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-02-26 22:48:32 10272 [ERROR] Column count of mysql.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50527, now running 50614. Please use mysql_upgrade to fix this error.
2014-02-26 22:48:32 10272 [ERROR] Column count of mysql.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50527, now running 50614. Please use mysql_upgrade to fix this error.
2014-02-26 22:48:32 10272 [ERROR] Column count of mysql.events_waits_history_long is wrong. Expected 19, found 16. Created with MySQL 50527, now running 50614. Please use mysql_upgrade to fix this error.
2014-02-26 22:48:32 10272 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_thread_by_event_name: expected column 'THREAD_ID' at position 0 to have type bigint(20), found type int(11).
2014-02-26 22:48:32 10272 [ERROR] Column count of mysql.file_summary_by_event_name is wrong. Expected 23, found 5. Created with MySQL 50527, now running 50614. Please use mysql_upgrade to fix this error.
2014-02-26 22:48:32 10272 [ERROR] Column count of mysql.file_summary_by_instance is wrong. Expected 25, found 6. Created with MySQL 50527, now running 50614. Please use mysql_upgrade to fix this error.
2014-02-26 22:48:32 10272 [ERROR] Incorrect definition of table performance_schema.mutex_instances: expected column 'LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2014-02-26 22:48:32 10272 [ERROR] Incorrect definition of table performance_schema.rwlock_instances: expected column 'WRITE_LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2014-02-26 22:48:32 10272 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50527, now running 50614. Please use mysql_upgrade to fix this error.
2014-02-26 22:48:32 10272 [Note] Event Scheduler: Loaded 0 events
2014-02-26 22:48:32 10272 [Note] mysql\bin\mysqld.exe: ready for connections.


A quick run of mysql_upgrade fails:
Code

c:\AMPPS\mysql\bin>mysql_upgrade
Looking for 'mysql.exe' as: c:\AMPPS\mysql\bin\mysql.exe
Looking for 'mysqlcheck.exe' as: c:\AMPPS\mysql\bin\mysqlcheck.exe
Running 'mysqlcheck' with connection arguments: "--port=3306" "--socket=C:/AMPPS/mysql/mysql.sock"
Warning: Using a password on the command line interface can be insecure.
Running 'mysqlcheck' with connection arguments: "--port=3306" "--socket=C:/AMPPS/mysql/mysql.sock"
Warning: Using a password on the command line interface can be insecure.
mysql.columns_priv                                OK
mysql.db                                          OK
mysql.event                                        OK
mysql.func                                        OK
mysql.general_log                                  OK
mysql.help_category                                OK
mysql.help_keyword                                OK
mysql.help_relation                                OK
mysql.help_topic                                  OK
mysql.host                                        OK
mysql.innodb_index_stats
Error    : Table 'mysql.innodb_index_stats' doesn't exist
status  : Operation failed
mysql.ndb_binlog_index                            OK
mysql.plugin                                      OK
mysql.proc                                        OK
mysql.procs_priv                                  OK
mysql.proxies_priv                                OK
mysql.servers                                      OK
mysql.slow_log                                    OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                              OK
mysql.time_zone_transition                        OK
mysql.time_zone_transition_type                    OK
mysql.user                                        OK

Repairing tables
mysql.innodb_index_stats
Error    : Table 'mysql.innodb_index_stats' doesn't exist
status  : Operation failed
Running 'mysql_fix_privilege_tables'...
Warning: Using a password on the command line interface can be insecure.
ERROR 1146 (42S02) at line 66: Table 'mysql.innodb_index_stats' doesn't exist
ERROR 1243 (HY000) at line 67: Unknown prepared statement handler (stmt) given to EXECUTE
ERROR 1243 (HY000) at line 68: Unknown prepared statement handler (stmt) given to DEALLOCATE PREPARE
ERROR 1146 (42S02) at line 1886: Table 'mysql.innodb_index_stats' doesn't exist
FATAL ERROR: Upgrade failed


db's function in the WordPress installations, but each throws multiple errors on use. Examples:
Code

2014-02-26 22:51:47 10272 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-02-26 22:51:47 10272 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-02-26 22:51:48 10272 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-02-26 22:51:49 10272 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.


Code
2014-02-26 22:56:49 1e24 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.
2014-02-26 22:56:49 1e24 InnoDB: Error: Fetch of persistent statistics requested for table "themes"."d6qhq1x_ninja_forms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2014-02-26 22:57:33 1e24 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.
2014-02-26 22:57:33 1e24 InnoDB: Error: Fetch of persistent statistics requested for table "enterprise"."d6qhq1x_bwps_lockouts" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2014-02-26 22:57:33 1e24 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.
2014-02-26 22:57:33 1e24 InnoDB: Error: Fetch of persistent statistics requested for table "enterprise"."d6qhq1x_ninja_forms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.


Each of 63 databases throw the last two errors.  So I'm not really sure of what strategy to follow: attempt repairs? is a second, fresh installation of AMPPS somehow better? How can I get back to a clean upgrade path?

Thanks for any advice.
IP: --   

upgrade to 2.3, all sited "database error"
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

You can try following this post for solution.
http://www.softaculous.com/board/index.php?tid=5041&title=1146_MySQL_error#p18162

-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
Quote

1. Go to Ampps\mysql\data

2. Create a "Backup" folder under data

3. Move those files to your Backup folder
Quote
innodb_index_stats.frm
innodb_index_stats.ibd
innodb_table_stats.frm
innodb_table_stats.ibd
slave_master_info.ibd
slave_relay_log_info.frm
slave_relay_log_info.ibd
slave_worker_info.frm
slave_worker_info.ibd
4. now open control panel and click on start under mysql


move files:  now mysql will not start (at all)

restore files: mysql stays broken (will not start)

?
IP: --   

upgrade to 2.3, all sited "database error"
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Clear log file. And try starting mysql. Attach the whole log file here.

-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
cleared; attached; thanks!

Code
2014-02-27 00:55:48 8060 [Note] Plugin 'FEDERATED' is disabled.
2014-02-27 00:55:48 8060 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-27 00:55:48 8060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-27 00:55:48 8060 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-27 00:55:48 8060 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-27 00:55:48 8060 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-02-27 00:55:48 8060 [Note] InnoDB: Completed initialization of buffer pool
2014-02-27 00:55:48 8060 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-27 00:55:48 8060 [Note] InnoDB: 128 rollback segment(s) are active.
2014-02-27 00:55:48 8060 [Note] InnoDB: Waiting for purge to start
2014-02-27 00:55:49 8060 [Note] InnoDB: 5.6.14 started; log sequence number 380693392
mysql\bin\mysqld.exe: File '.\mysql-bin.000015' not found (Errcode: 2 - No such file or directory)
2014-02-27 00:55:49 8060 [ERROR] Failed to open log (file '.\mysql-bin.000015', errno 2)
2014-02-27 00:55:49 8060 [ERROR] Could not open log file
2014-02-27 00:55:49 8060 [ERROR] Can't init tc log
2014-02-27 00:55:49 8060 [ERROR] Aborting

2014-02-27 00:55:49 8060 [Note] Binlog end
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'partition'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_METRICS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_CMP'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'INNODB_TRX'
2014-02-27 00:55:49 8060 [Note] Shutting down plugin 'InnoDB'
2014-02-27 00:55:49 8060 [Note] InnoDB: FTS optimize thread exiting.
2014-02-27 00:55:49 8060 [Note] InnoDB: Starting shutdown...
2014-02-27 00:55:50 8060 [Note] InnoDB: Shutdown completed; log sequence number 380693402
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'BLACKHOLE'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'ARCHIVE'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'MRG_MYISAM'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'MyISAM'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'MEMORY'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'CSV'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'sha256_password'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'mysql_old_password'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'mysql_native_password'
2014-02-27 00:55:50 8060 [Note] Shutting down plugin 'binlog'
2014-02-27 00:55:50 8060 [Note] mysql\bin\mysqld.exe: Shutdown complete

IP: --   

upgrade to 2.3, all sited "database error"
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

In Ampps/mysql/data folder delete mysql-bin.* files including .index file.

Try starting then.

-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
15 files deleted; mysql does not start; no change in log file

:squi:
IP: --   

upgrade to 2.3, all sited "database error"
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Clear the log again and start. Let us know the log then

-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
re-cleared, re-started; re-joice (?);

Code
2014-02-27 01:34:59 9692 [Note] Plugin 'FEDERATED' is disabled.
2014-02-27 01:34:59 9692 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-27 01:34:59 9692 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-27 01:34:59 9692 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-27 01:34:59 9692 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-27 01:34:59 9692 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-02-27 01:34:59 9692 [Note] InnoDB: Completed initialization of buffer pool
2014-02-27 01:34:59 9692 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-27 01:35:00 9692 [Note] InnoDB: 128 rollback segment(s) are active.
2014-02-27 01:35:00 9692 [Note] InnoDB: Waiting for purge to start
2014-02-27 01:35:00 9692 [Note] InnoDB: 5.6.14 started; log sequence number 380693422
2014-02-27 01:35:00 9692 [Note] Server hostname (bind-address): '*'; port: 3306
2014-02-27 01:35:00 9692 [Note] IPv6 is available.
2014-02-27 01:35:00 9692 [Note]  - '::' resolves to '::';
2014-02-27 01:35:00 9692 [Note] Server socket created on IP: '::'.
2014-02-27 01:35:00 9692 [Note] Event Scheduler: Loaded 0 events
2014-02-27 01:35:00 9692 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14-log'  socket: ''  port: 3306  MySQL Community Server (GPL)



Everything looks clear, until I launch a few sites, then some consistent errors appear.

Code

2014-02-27 01:37:33 3858 InnoDB: Error: Fetch of persistent statistics requested for table "theme"."d6qhq1x_ninja_forms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2014-02-27 01:39:11 3770 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.

2014-02-27 01:39:11 3770 InnoDB: Error: Fetch of persistent statistics requested for table "enterprise"."d6qhq1x_bwps_lockouts" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2014-02-27 01:39:11 3770 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.
2014-02-27 01:39:11 3770 InnoDB: Error: Fetch of persistent statistics requested for table "enterprise"."d6qhq1x_ninja_forms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2014-02-27 01:39:46 3770 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.

2014-02-27 01:39:46 3770 InnoDB: Error: Fetch of persistent statistics requested for table "news"."d6qhq1x_bwps_lockouts" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2014-02-27 01:39:46 3770 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.
2014-02-27 01:39:46 3770 InnoDB: Error: Fetch of persistent statistics requested for table "news"."d6qhq1x_ninja_forms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.



Thank you for your patience and guidance.

Now to re-attempt the 2.3 upgrade again.
IP: --   

upgrade to 2.3, all sited "database error"
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Can you install teamviewer so we take control over your desktop and look into this ?

You can open a ticket ( http://ampps.com/support ) and leave TeamViewers details there.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
And... it's back, or something like it.  Had to reboot and on restart:

Code
InnoDB: Error: could not open single-table tablespace file .\sandbox\d6qhq1x_bwps_log.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-03-01 16:59:22 13304 [Note] Plugin 'FEDERATED' is disabled.
2014-03-01 16:59:22 13304 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-01 16:59:22 13304 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-01 16:59:22 13304 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-01 16:59:22 13304 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-01 16:59:22 13304 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-03-01 16:59:22 13304 [Note] InnoDB: Completed initialization of buffer pool
2014-03-01 16:59:22 13304 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-01 16:59:22 13304 [Note] InnoDB: The log sequence numbers 380693432 and 380693432 in ibdata files do not match the log sequence number 380818777 in the ib_logfiles!
2014-03-01 16:59:22 13304 [Note] InnoDB: Database was not shutdown normally!
2014-03-01 16:59:22 13304 [Note] InnoDB: Starting crash recovery.
2014-03-01 16:59:22 13304 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-01 16:59:22 13304 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace sandbox/d6qhq1x_bwps_log which uses space ID: 2 at filepath: .\sandbox\d6qhq1x_bwps_log.ibd
InnoDB: Error: could not open single-table tablespace file .\sandbox\d6qhq1x_bwps_log.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
IP: --   

upgrade to 2.3, all sited "database error"
ant0n
Group: Member
Post Group: Newbie
Posts: 20
Status:
Used the recommended "InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf" (=1) to enable start of mysql.  Dropped offending 'sandbox' database. Restored mysql configuration to default. Startup is normal.

Yay!

Run Ampps-2.3-setup.exe to upgrade >  Startup crash

Quote
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


I could troll through that all day and still not have a clue where to start any
repair.

Suggestions appreciated.

Code
2014-03-02 16:41:03 4168 [Note] mysql\bin\mysqld.exe: Shutdown complete

2014-03-02 17:05:22 15316 [Warning] You need to use --log-bin to make --binlog-format work.
2014-03-02 17:05:22 15316 [Note] Plugin 'FEDERATED' is disabled.
2014-03-02 17:05:22 15316 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-03-02 17:05:22 15316 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-02 17:05:22 15316 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-02 17:05:22 15316 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-02 17:05:22 15316 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-02 17:05:22 15316 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-03-02 17:05:22 15316 [Note] InnoDB: Completed initialization of buffer pool
2014-03-02 17:05:22 15316 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-02 17:05:23 15316 [Note] InnoDB: 128 rollback segment(s) are active.
2014-03-02 17:05:23 15316 [Note] InnoDB: Waiting for purge to start
2014-03-02 17:05:23 15316 [Note] InnoDB: 5.6.16 started; log sequence number 380914759
2014-03-02 17:05:23 15316 [Note] Server hostname (bind-address): '*'; port: 3306
2014-03-02 17:05:23 15316 [Note] IPv6 is available.
2014-03-02 17:05:23 15316 [Note]  - '::' resolves to '::';
2014-03-02 17:05:23 15316 [Note] Server socket created on IP: '::'.
InnoDB: Error: tablespace id is 493 in the data dictionary
InnoDB: but in file .\mysql\slave_master_info.ibd it is 4!
2014-03-02 17:05:23 294c  InnoDB: Assertion failure in thread 10572 in file fil0fil.cc line 796
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:05:23 UTC - mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133777 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x12d78338
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
1268300    mysqld.exe!my_thread_name()
14a1d3d    mysqld.exe!my_mb_ctype_mb()
12ed380    mysqld.exe!murmur3_32()
12f0f38    mysqld.exe!murmur3_32()
13bfc93    mysqld.exe!murmur3_32()
13c04ed    mysqld.exe!murmur3_32()
1320353    mysqld.exe!murmur3_32()
137b0a4    mysqld.exe!murmur3_32()
137b161    mysqld.exe!murmur3_32()
137b656    mysqld.exe!murmur3_32()
132482f    mysqld.exe!murmur3_32()
132495a    mysqld.exe!murmur3_32()
1328e58    mysqld.exe!murmur3_32()
128f9ee    mysqld.exe!murmur3_32()
101f5e6    mysqld.exe!?ha_open@handler@@QAEHPAUTABLE@@PBDHH@Z()
110b773    mysqld.exe!?open_table_from_share@@YAHPAVTHD@@PAUTABLE_SHARE@@PBDIIIPAUTABLE@@_N@Z()
10671f4    mysqld.exe!?open_table@@YA_NPAVTHD@@PAUTABLE_LIST@@PAVOpen_table_context@@@Z()
1067887    mysqld.exe!?recover_from_failed_open@Open_table_context@@QAE_NXZ()
1068946    mysqld.exe!?open_tables@@YA_NPAVTHD@@PAPAUTABLE_LIST@@PAIIPAVPrelocking_strategy@@@Z()
1068b74    mysqld.exe!?open_and_lock_tables@@YA_NPAVTHD@@PAUTABLE_LIST@@_NIPAVPrelocking_strategy@@@Z()
1068d29    mysqld.exe!?open_n_lock_single_table@@YAPAUTABLE@@PAVTHD@@PAUTABLE_LIST@@W4thr_lock_type@@IPAVPrelocking_strategy@@@Z()
125f41c    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
125d1b2    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257374    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257444    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257689    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1257ca2    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1253574    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
1012548    mysqld.exe!?win_main@@YAHHPAPAD@Z()
10127e7    mysqld.exe!?mysql_service@@YAHPAX@Z()
149c89a    mysqld.exe!my_mb_ctype_mb()
75c6336a    kernel32.dll!BaseThreadInitThunk()
77b39f72    ntdll.dll!RtlInitializeExceptionChain()
77b39f45    ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.



More detail:  pastebin


IP: --   

« Previous    Next »

Threaded Mode | Print  

1


Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is April 27, 2024, 4:30 pm.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.028